5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
- Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-3: Domains

Alpha Domain Additional Attributes


From the Alpha Domains overlay, you have an Additional Attributesoption. The Alpha domain Additional Attributes overlay is shown below.

Alpha Domain Additional Attributes Overlay

The Alpha Domain Additional Attributes Overlay contains the following fields:

Default Value establishes a modifiable starting value for all image items whenever they are first displayed in add mode in an input image, unless modified by a user. If blank, there is no starting value displayed on the image.

Range Checks defines a series of allowable values that APPX uses for online data validation. The first component represents the relation. The options are:

EQ (equal to)

NE (not equal to)

GT (greater than)

LT (less than)

GE (greater than or equal to)

LE (less than or equal to)

IN (includes)

The second component represents the value assigned to the relation. If you enter two relations, APPX infers an AND relationship.

Blanks Allowed indicates whether or not blanks are permitted and, if so, where they can be placed. The Blanks Allowed options are:

NONE, The field cannot contain blanks.

TRAILING, Blanks are permitted only when positioned to the right of the far right-hand (non-constant) character in a field. Trailing constant characters are treated as trailing blanks for the purpose of applying this restriction.

ANYWHERE, Blanks can be entered in any position within a field.

The default is ANYWHERE.

Alignment, determines whether or not data in a field is aligned for storage and/or display and, if so, the type of alignment. The Alignment options are:

NONE, Data is not aligned for either storage or display purposes.

LEFT, Data is aligned with the far left-hand character position in a field.

RIGHT, Data is aligned with the far right-hand character position in a field.

CENTERED, Data displays in the center of a field.

JUSTIFIED, Data is aligned with both the far left-and right-hand character positions in a field, and distributed to occupy the entire field. Where necessary, data is padded with spaces.

The default is NONE. The figure below shows the different alignment options.

This type is aligned flush with the left margin.

This type is aligned flush with the right margin.

This type is centered within the left and right margins.

This type is aligned flush with both margins.

Left

Right

Centered

Justified

Alignment Options

Pad Character indicates the character to be used instead of leading and trailing spaces in a field.

Translate? indicates if the value of the work field should be translated into a designated language if APPX's Language Translation feature is being used. Since this option does not require a validation table for a work field (unlike a file field), it is the designer's responsibility to ensure that a translatable work field without a validation table is read only. Click the checkbox to toggle between 'yes' (Y using Character Mode), 'no' (N using Character Mode), and unknown (Y, N, or blank using Character Mode) values. If the translation feature is not in use, retain the default value of (blank using Character Mode).

Require Table Value? indicates if fields based on this domain require one of the validation table values to be entered. To force the user to enter one of the defined values, click the checkbox to toggle it to 'yes' (Y using Character Mode). If a 'no' (N using Character Mode) value is selected, the validation table shown when the user selects the list feature, is advisory only and the user can enter a value not listed in the table. If there is no validation table defined, this option does not apply and cannot be selected. If Translate? is , this option should also be (Y using Character Mode).

Application Design Manual                                         "Powered by Appx Software"

987

©2006 By APPX Software, Inc. All Rights Reserved